|
|
| Author |
Thread Statistics | Show CCP posts - 142 post(s) |
Bad Bobby
Bring Me Sunshine
In Tea We Trust
525
   |
Posted - 2014.07.22 19:00:00 -
[1] - Quote
New S&I window doesn't stack.
New S&I window doesn't resize properly.
New S&I window doesn't fully support drag and drop functionality.
Go to Jobs tab, right click on a BPO, select "Use Blueprint"... nothing happens.
It doesn't appear to be possible to change the ME/TE levels of blueprints when in preview mode. |
Bad Bobby
Bring Me Sunshine
In Tea We Trust
542
|
Posted - 2014.07.23 16:47:00 -
[2] - Quote
Kenneth Feld wrote:The whole SC/Titan customer service stuff is a joke
I have had them on speeddial for 2 days
You're lucky. You're getting a better response than I am.
All my recent dealings with CCP customer service have been case studies in how not to provide a customer with service.
It makes me want to throw my shoes at them through the internet tubes. |
Bad Bobby
Bring Me Sunshine
In Tea We Trust
542
|
Posted - 2014.07.23 16:53:00 -
[3] - Quote
Ryuu Towryk wrote:I really don't think this 6 week dev cycle is a good idea...
I'll have to disagree with you on that point. I think it is a good idea.
However, this release is an example of how not to use a 6 week Dev cycle. Because it is clear that many of the features deployed in this release needed more time to be developed, reviewed and tested. Therefore they should have postponed much of the content for 6 weeks, finished it to a higher standard and then released it in a good state. This is one of the very reasons why they have moved to a 6 week Dev cycle and yet they failed to avail themselves of it's advantages.
What we have recieved is an unpolished, feature light and bug heavy expansion... essentially the worst of all worlds. But it is not because of a 6 week Dev cycle. |
Bad Bobby
Bring Me Sunshine
In Tea We Trust
544
|
Posted - 2014.07.23 17:18:00 -
[4] - Quote
Pheusia wrote:Bad Bobby wrote:Ryuu Towryk wrote:I really don't think this 6 week dev cycle is a good idea... I'll have to disagree with you on that point. I think it is a good idea. However, this release is an example of how not to use a 6 week Dev cycle. Because it is clear that many of the features deployed in this release needed more time to be developed, reviewed and tested. Therefore they should have postponed much of the content for 6 weeks, finished it to a higher standard and then released it in a good state. This is one of the very reasons why they have moved to a 6 week Dev cycle and yet they failed to avail themselves of it's advantages. What we have recieved is an unpolished, feature light and bug heavy expansion... essentially the worst of all worlds. But it is not because of a 6 week Dev cycle. Well most of the stuff in Crius was originally slated for Kronos, which was the last 6 month expansion.
Which also doesn't reinforce any criticism of the 6 week Dev cycle.
It is certainly a criticism of CCPs ability to deliver quality content on schedule. And I think they owe the players an appology for Crius. But proper use of their 6 week Dev cycle could have fixed this. |
Bad Bobby
Bring Me Sunshine
In Tea We Trust
546
|
Posted - 2014.07.23 17:39:00 -
[5] - Quote
Lady Rift wrote:Bad Bobby wrote:Pheusia wrote:Bad Bobby wrote:Ryuu Towryk wrote:I really don't think this 6 week dev cycle is a good idea... I'll have to disagree with you on that point. I think it is a good idea. However, this release is an example of how not to use a 6 week Dev cycle. Because it is clear that many of the features deployed in this release needed more time to be developed, reviewed and tested. Therefore they should have postponed much of the content for 6 weeks, finished it to a higher standard and then released it in a good state. This is one of the very reasons why they have moved to a 6 week Dev cycle and yet they failed to avail themselves of it's advantages. What we have recieved is an unpolished, feature light and bug heavy expansion... essentially the worst of all worlds. But it is not because of a 6 week Dev cycle. Well most of the stuff in Crius was originally slated for Kronos, which was the last 6 month expansion. Which also doesn't reinforce any criticism of the 6 week Dev cycle. It is certainly a criticism of CCPs ability to deliver quality content on schedule. And I think they owe the players an appology for Crius. But proper use of their 6 week Dev cycle could have fixed this. That's the problem CCP has shown they cant properly use the 6 week cycle. Other games and companies maybe but not this one.They will want to push something out every 6 weeks no matter how broken it is instead of having to skip one expansion or it be really really light in content. Plus their stated things they will be working on include reworking some of the most ignored and worst systems in the game (corp management and POS's)
It's too early to tell. This is their first go at it and they will need time to perfect it.
One can hope that Crius will demonstrate to them the need for stricter quality gateways on what can or cannot be deployed. If it is in poor condition, or cannot be demonstrated to be in good condition, it doesn't release, you move to the next window. I'm personally very familiar with this process, as well as the difficulties in moving a company from one release model to another, so I'm more than willing to cut them some slack.
But they do need to learn fast. |
Bad Bobby
Bring Me Sunshine
In Tea We Trust
546
|
Posted - 2014.07.23 17:58:00 -
[6] - Quote
Xaevryn Ulvek wrote:Anyone else think we should seriously have a rollback until CCP figures everything out? I'm not sure a rollback is going to be a net improvement in our situation. I think it needs to be fixed while it lives on Tranquility, which I agree is a terrible situation to be in. But I don't think pulling it back out will be worth the technical issues that will likely cause.
Xaevryn Ulvek wrote:I know we function as your wageless testers CCP, but there's a limit. Part of the problem is that it didn't get to spend enough time on a working Sisi server for the wageless testers to perform their magic.
|
Bad Bobby
Bring Me Sunshine
In Tea We Trust
546
|
Posted - 2014.07.23 18:56:00 -
[7] - Quote
Tom Parmala wrote:Retar Aveymone wrote:For other jobs, are we required to still pretend those jobs are in the pos, or can they just be delivered to the station? And can the pos be torn down, or should we maintain the pos until the jobs are delivered, even though they're supposedly at the pos? i would like to know this as well, pls answer. CCP Claymore wrote:For all jobs that are not supercaps, you are allowed to deliver them in station.They are now in the station and not in the pos so the pos can also be removed. |
Bad Bobby
Bring Me Sunshine
In Tea We Trust
547
|
Posted - 2014.07.24 10:38:00 -
[8] - Quote
Aluka 7th wrote:CCP RubberBAND wrote:Irin Fidard wrote:Okey, so to show the devs how damn slow their new and fancy Industry UI is I made a screen capture to show what I have to endure everytime I open up the Industry, change any filter setting or god forbid - search for a blueprint. please make it so that it only loads what I actually see in the UI. It seems that it loads the whole list of all BPC directly into the UI instead of virtualizing it and only show what is actually visible at any given time. http://imgur.com/hKZEnTe Out of curiosity how many blueprints do you have? We are aware of performance hit, but this should only affect users with tens of thousands of blueprints. I have similar delay, about 5000 prints.
About the same for me.
All of mine are stored in corp hangars rather than in my own hangar. Many are in containers.
God knows what it would have been like if I hadn't torn down all my POSes and sold off 80% of my blueprints in preparation for Crius! |
Bad Bobby
Bring Me Sunshine
In Tea We Trust
547
|
Posted - 2014.07.24 11:19:00 -
[9] - Quote
CCP Greyscale wrote:All the known issues should be listed in the "known issues" list in the first post of this thread.
So we are to assume that the issues that aren't being added to the list are things we'll just have to accept? |
Bad Bobby
Bring Me Sunshine
In Tea We Trust
552
|
Posted - 2014.07.24 15:03:00 -
[10] - Quote
CCP RubberBAND wrote:For users with many blueprints please refer to: this threadIn summary blueprints in a password protected container (with a password), will not be displayed in the Blueprint Browser. This should allow those of you who have blueprints you don't want in the browser to hide them (which will also improve the performance). Is there a plan to improve performance for those that have lots of blueprints and still want to be able to access them?
|
|
|
|
|
| |
|